book: cover UFCS in Syntax Index #31222
Conversation
| @@ -117,6 +117,9 @@ | |||
| * `super::path`: path relative to the parent of the current module. See [Crates and Modules (Re-exporting with `pub use`)]. | |||
| * `type::ident`: associated constants, functions, and types. See [Associated Types]. | |||
| * `<type>::…`: associated item for a type which cannot be directly named (*e.g.* `<&T>::…`, `<[T]>::…`, *etc.*). See [Associated Types]. | |||
| * `Trait::method(…)`: disambiguating a method call by naming the trait which defines it. See [Universal Function Call Syntax]. | |||
| * `Type::method(…)`: disambiguating a method call by naming the type for which it's defined. See [Universal Function Call Syntax]. | |||
| * `<Type as Trait>::method(…)`: disambiguating a method call by naming the trait _and_ type. See [Universal Function Call Syntax (Angle-bracket Form)]. | |||
There was a problem hiding this comment.
Not sure if I should follow the (IMO odd) all-lowercase convention for these entries.
|
Updated to follow the capitalization convention and cover the case of associated types (e.g. |
|
So, one thing here is that we've been meaning to rename UFCS for a long time, because it's a really bad name. /cc @eddyb @rust-Lang/core On Jan 26, 2016, 14:37 -0500, Alex [email protected], wrote:
|
|
How about something like "Fully Qualified Item" (by analogy with FQDN)? |
|
I agree on using "fully qualified", although there are "partially qualified" forms too. @steveklabnik I don't think that worked. cc @rust-lang/core |
|
I think I'm gonna merge this, since it's not fair to block it on renaming UFCS. I just wanted to raise the issue. @bors: r+ rollup |
|
📌 Commit 2f633b2 has been approved by |
|
⌛ Testing commit 2f633b2 with merge 6d9bdac... |
|
💔 Test failed - auto-mac-32-opt |
|
@bors: retry On Wed, Jan 27, 2016 at 12:26 PM, bors [email protected] wrote:
|
r? @steveklabnik